Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc74ab3117492ab246c446789d99154ae8e1e9254401a3bde9b57eeac85ff1f9

Tx prefix hash: 6eb314140a3a94f803809daab3d7fdde7e5192722f4af21aa311d102479499fe
Tx public key: 6692fb24f6e9f1909c81540f2002c8d2d2e313e63e8dcc3dfa822990293ea8d1
Timestamp: 1713455504 Timestamp [UCT]: 2024-04-18 15:51:44 Age [y:d:h:m:s]: 01:221:05:20:48
Block: 1003281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416797 RingCT/type: yes/0
Extra: 016692fb24f6e9f1909c81540f2002c8d2d2e313e63e8dcc3dfa822990293ea8d102110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7490f86d6526181867acbf57c6d79856b7f1657d94cdeeda15f0664d2096a3fc 0.600000000000 1463811 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": 1003291, "vin": [ { "gen": { "height": 1003281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7490f86d6526181867acbf57c6d79856b7f1657d94cdeeda15f0664d2096a3fc" } } ], "extra": [ 1, 102, 146, 251, 36, 246, 233, 241, 144, 156, 129, 84, 15, 32, 2, 200, 210, 210, 227, 19, 230, 62, 141, 204, 61, 250, 130, 41, 144, 41, 62, 168, 209, 2, 17, 0, 0, 0, 6, 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