Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91708a561ab011835c1c756e9ed431fe6b6290d43cd043776a89d053e03f2be6

Tx prefix hash: 430150c0bad0cd5361ea77a012c8673385eb94a5a412ab7ae928133a71635034
Tx public key: 409bd2f3c7aff77345b807c05a616e8d699b059e8ff6a3e3aabaa2c09837763c
Timestamp: 1723806394 Timestamp [UCT]: 2024-08-16 11:06:34 Age [y:d:h:m:s]: 00:259:13:33:49
Block: 1089115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185398 RingCT/type: yes/0
Extra: 01409bd2f3c7aff77345b807c05a616e8d699b059e8ff6a3e3aabaa2c09837763c021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1c317517b91671c8585b78e5aa470d1084024746b990870ddd10bd59b32ea15 0.600000000000 1563734 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": 1089125, "vin": [ { "gen": { "height": 1089115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1c317517b91671c8585b78e5aa470d1084024746b990870ddd10bd59b32ea15" } } ], "extra": [ 1, 64, 155, 210, 243, 199, 175, 247, 115, 69, 184, 7, 192, 90, 97, 110, 141, 105, 155, 5, 158, 143, 246, 163, 227, 170, 186, 162, 192, 152, 55, 118, 60, 2, 17, 0, 0, 0, 1, 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