Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb5e27c9b4b16a00d80fb9612515b39aa84def96f9bb820b0682bae3cf9325cc

Tx prefix hash: bb2bd0def0afbe1e36bdf9b0dd6e5caef96debfb9664dabe95e7f10e97bea2a1
Tx public key: 8ce76c954886746b3a99d069687015a70b1d50e0309400e2af1e689afdb357d5
Timestamp: 1728485061 Timestamp [UCT]: 2024-10-09 14:44:21 Age [y:d:h:m:s]: 00:167:22:54:06
Block: 1127902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119812 RingCT/type: yes/0
Extra: 018ce76c954886746b3a99d069687015a70b1d50e0309400e2af1e689afdb357d502110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c364efe0dc2fec50bd83002d8d8595a1e3e32120e7ffa2d4a4344a1ef3b391bc 0.600000000000 1610715 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": 1127912, "vin": [ { "gen": { "height": 1127902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c364efe0dc2fec50bd83002d8d8595a1e3e32120e7ffa2d4a4344a1ef3b391bc" } } ], "extra": [ 1, 140, 231, 108, 149, 72, 134, 116, 107, 58, 153, 208, 105, 104, 112, 21, 167, 11, 29, 80, 224, 48, 148, 0, 226, 175, 30, 104, 154, 253, 179, 87, 213, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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