Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bab4e9aad90c95494146654a0d6c0b011df092c2462ce723994b84304d8c08b

Tx prefix hash: 3f4e8cadaa11f66dc458329d3718c6c02c4abf3e8407580052d0b04da2f27abd
Tx public key: e4d8e4d9fae02c687da2538df3f801736d6d0f5074dd5edaf47a62998af8e391
Timestamp: 1694805753 Timestamp [UCT]: 2023-09-15 19:22:33 Age [y:d:h:m:s]: 01:276:23:14:10
Block: 848868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458959 RingCT/type: yes/0
Extra: 01e4d8e4d9fae02c687da2538df3f801736d6d0f5074dd5edaf47a62998af8e3910211000000054b8f5122000000000000000000

1 output(s) for total of 0.944817639000 dcy

stealth address amount amount idx
00: 427bd7371ca2da6d0c2a0fae7ee0754d3a3a6c24aca7a5d468dab2c2d9729fb2 0.944817639000 1302498 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": 848878, "vin": [ { "gen": { "height": 848868 } } ], "vout": [ { "amount": 944817639, "target": { "key": "427bd7371ca2da6d0c2a0fae7ee0754d3a3a6c24aca7a5d468dab2c2d9729fb2" } } ], "extra": [ 1, 228, 216, 228, 217, 250, 224, 44, 104, 125, 162, 83, 141, 243, 248, 1, 115, 109, 109, 15, 80, 116, 221, 94, 218, 244, 122, 98, 153, 138, 248, 227, 145, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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