Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fba121e17b5431b81f28328e9df2927eade9af44ba2a94e7601b8aebe09ad9b9

Tx prefix hash: 3c754c4d76697275b3a69af5d43da33831f3a39b0233822e88d51523f6551391
Tx public key: 9cbce13cc3e1f3e3cfb0eb89ff243f25e3d166dad130087372b1dde02ba1a8ef
Timestamp: 1709491160 Timestamp [UCT]: 2024-03-03 18:39:20 Age [y:d:h:m:s]: 01:105:17:05:16
Block: 970440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336498 RingCT/type: yes/0
Extra: 019cbce13cc3e1f3e3cfb0eb89ff243f25e3d166dad130087372b1dde02ba1a8ef02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0b49d920a330c71a0dc6e631289fdea2a98b2e379f888105da9ec6e071da95d 0.600000000000 1430293 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": 970450, "vin": [ { "gen": { "height": 970440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0b49d920a330c71a0dc6e631289fdea2a98b2e379f888105da9ec6e071da95d" } } ], "extra": [ 1, 156, 188, 225, 60, 195, 225, 243, 227, 207, 176, 235, 137, 255, 36, 63, 37, 227, 209, 102, 218, 209, 48, 8, 115, 114, 177, 221, 224, 43, 161, 168, 239, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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