Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49bdd51a802084c1336de7fc4527bc2bfef7f3feedccc00d71e49ad8d0a0a7af

Tx prefix hash: a38363223784f15b4634720e51ad684d5ebca7666df4757d5b9d524db461afb1
Tx public key: f2704a4749ca6352926dfe0a2cfd427e75f480a333757299a7b8446e4ca8f184
Timestamp: 1727527656 Timestamp [UCT]: 2024-09-28 12:47:36 Age [y:d:h:m:s]: 00:056:18:58:51
Block: 1119965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40583 RingCT/type: yes/0
Extra: 01f2704a4749ca6352926dfe0a2cfd427e75f480a333757299a7b8446e4ca8f184021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fce69d2f7e7a6965a4760c2fa6b3a8b6da71dccf0ff7dc3b347724a56af0ba3e 0.600000000000 1601712 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": 1119975, "vin": [ { "gen": { "height": 1119965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fce69d2f7e7a6965a4760c2fa6b3a8b6da71dccf0ff7dc3b347724a56af0ba3e" } } ], "extra": [ 1, 242, 112, 74, 71, 73, 202, 99, 82, 146, 109, 254, 10, 44, 253, 66, 126, 117, 244, 128, 163, 51, 117, 114, 153, 167, 184, 68, 110, 76, 168, 241, 132, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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