Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8aa36e958dd5232ac209f6f3238b4ced8e2a1b0b15b45ac48ab25a1a0e6279e3

Tx prefix hash: f642f6b0f873ea56a2c8877175c1fed1fb517e55b7b2a25738df2327093093b8
Tx public key: ede036a387d59649857834f9c50b178bf499b9892f8736cdf4e11b14d596c74c
Timestamp: 1701217108 Timestamp [UCT]: 2023-11-29 00:18:28 Age [y:d:h:m:s]: 01:087:13:58:26
Block: 901824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323722 RingCT/type: yes/0
Extra: 01ede036a387d59649857834f9c50b178bf499b9892f8736cdf4e11b14d596c74c0211000000014b8f5122000000000000000000

1 output(s) for total of 0.630786956000 dcy

stealth address amount amount idx
00: b9db2c099bd59f3690b30f7ba177fc15e4d6d89ae9de8dbf1e186a3f27b49c17 0.630786956000 1358417 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": 901834, "vin": [ { "gen": { "height": 901824 } } ], "vout": [ { "amount": 630786956, "target": { "key": "b9db2c099bd59f3690b30f7ba177fc15e4d6d89ae9de8dbf1e186a3f27b49c17" } } ], "extra": [ 1, 237, 224, 54, 163, 135, 213, 150, 73, 133, 120, 52, 249, 197, 11, 23, 139, 244, 153, 185, 137, 47, 135, 54, 205, 244, 225, 27, 20, 213, 150, 199, 76, 2, 17, 0, 0, 0, 1, 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