Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b713b09fd38c8365f411dcec9f6523a7f241a341b216b201367b67234ff86b10

Tx prefix hash: 7cbc0b8287dc6cd0f1eed73a3a37d4866c750dbd34f40a8c554075f218c6b125
Tx public key: 1025473c182d29c6af537a2bd02e2b75f3aa80064a5271314beefc5a90467f42
Timestamp: 1577556817 Timestamp [UTC]: 2019-12-28 18:13:37 Age [y:d:h:m:s]: 06:266:19:46:20
Block: 33691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1605256 RingCT/type: yes/0
Extra: 011025473c182d29c6af537a2bd02e2b75f3aa80064a5271314beefc5a90467f420211000000064ac5aa02000000000000000000

1 output(s) for total of 0.474644647847 xmr

stealth address amount amount idx tag
00: 625364f4bc50ba2df937b14cbeebe38c77fd2dfd498575f5e64a13d41b3b20ee 0.474644647847 56507 of 0 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 33701, "vin": [ { "gen": { "height": 33691 } } ], "vout": [ { "amount": 474644647847, "target": { "key": "625364f4bc50ba2df937b14cbeebe38c77fd2dfd498575f5e64a13d41b3b20ee" } } ], "extra": [ 1, 16, 37, 71, 60, 24, 45, 41, 198, 175, 83, 122, 43, 208, 46, 43, 117, 243, 170, 128, 6, 74, 82, 113, 49, 75, 238, 252, 90, 144, 70, 127, 66, 2, 17, 0, 0, 0, 6, 74, 197, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: