Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a734dc80e5e3537a382e4c23edb6bb4aa5f4d1ff8f643c0ba2f44097752b8f7

Tx prefix hash: 524458e3df4ad95197599f3963277c2f78d9b3377899229118f1a683960930ea
Tx public key: 4f03ff803a5186f2bc50c8261020ab9a2f21ea9ef62200e48b7a3256bf13f7f8
Timestamp: 1578519364 Timestamp [UCT]: 2020-01-08 21:36:04 Age [y:d:h:m:s]: 05:027:01:27:24
Block: 41634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1169165 RingCT/type: yes/0
Extra: 014f03ff803a5186f2bc50c8261020ab9a2f21ea9ef62200e48b7a3256bf13f7f802110000000a4ac5aa02000000000000000000

1 output(s) for total of 446.735145046000 dcy

stealth address amount amount idx
00: 48bf066054b33064cfa8fae66df4ca8625df23a0d6749efeb1092bc4f9e7e9f3 446.735145046000 74328 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 dinasty-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": 41644, "vin": [ { "gen": { "height": 41634 } } ], "vout": [ { "amount": 446735145046, "target": { "key": "48bf066054b33064cfa8fae66df4ca8625df23a0d6749efeb1092bc4f9e7e9f3" } } ], "extra": [ 1, 79, 3, 255, 128, 58, 81, 134, 242, 188, 80, 200, 38, 16, 32, 171, 154, 47, 33, 234, 158, 246, 34, 0, 228, 139, 122, 50, 86, 191, 19, 247, 248, 2, 17, 0, 0, 0, 10, 74, 197, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8