Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f478801b73d4175ef634c55df59557e9fe0b40f3f22a0906edce2a19c4fc4e10

Tx prefix hash: cd7c2142cb36bb6cf18db6b2be2ff6bcaecaca3be18db5e1eff9d5ae7ad8df1e
Tx public key: 4ce37375d474d416173330f3e408907b623033451cfe3a66a33f8ff5e98bfd31
Timestamp: 1720873080 Timestamp [UCT]: 2024-07-13 12:18:00 Age [y:d:h:m:s]: 00:285:09:51:26
Block: 1064806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203917 RingCT/type: yes/0
Extra: 014ce37375d474d416173330f3e408907b623033451cfe3a66a33f8ff5e98bfd3102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62b902b3e7b6ad7fb46251ff26c3372fdec3c8b225f04461e6b7ce871195e44a 0.600000000000 1535345 of 15

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": 1064816, "vin": [ { "gen": { "height": 1064806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62b902b3e7b6ad7fb46251ff26c3372fdec3c8b225f04461e6b7ce871195e44a" } } ], "extra": [ 1, 76, 227, 115, 117, 212, 116, 212, 22, 23, 51, 48, 243, 228, 8, 144, 123, 98, 48, 51, 69, 28, 254, 58, 102, 163, 63, 143, 245, 233, 139, 253, 49, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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