Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa6e37a70093a0571f55f84d15d410a4b014850ddd6e4d4af40faba0eb77dcac

Tx prefix hash: 575113e359e1c2735e4e2df4cbdd79e121c734c37b666d530fc835da44c90363
Tx public key: b910cafa7f2816e4a1de8349d9a62943798fa2bae92fb4ba9c4db8055497c393
Timestamp: 1705376382 Timestamp [UCT]: 2024-01-16 03:39:42 Age [y:d:h:m:s]: 01:304:02:46:56
Block: 936296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476181 RingCT/type: yes/0
Extra: 01b910cafa7f2816e4a1de8349d9a62943798fa2bae92fb4ba9c4db8055497c3930211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60984f760609faf18bba57ce7b3d91094af4a5d0959c4677fcf5f53139b1cec9 0.600000000000 1394320 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": 936306, "vin": [ { "gen": { "height": 936296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60984f760609faf18bba57ce7b3d91094af4a5d0959c4677fcf5f53139b1cec9" } } ], "extra": [ 1, 185, 16, 202, 250, 127, 40, 22, 228, 161, 222, 131, 73, 217, 166, 41, 67, 121, 143, 162, 186, 233, 47, 180, 186, 156, 77, 184, 5, 84, 151, 195, 147, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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