Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b54291889048f70687094e130fac2a157d560a8195b9b208e9b8e4cb4da893a

Tx prefix hash: a9116a73fadb4ce0b4d2cb49d88bd7fd36f511beeb874a869095a01a1a5efebf
Tx public key: 0dc68d7fbc17ca6fa1d7b5f173932e40cf4578b0ffcd99d0fe0083abd10d4268
Timestamp: 1703703696 Timestamp [UCT]: 2023-12-27 19:01:36 Age [y:d:h:m:s]: 01:133:07:59:12
Block: 922456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356412 RingCT/type: yes/0
Extra: 010dc68d7fbc17ca6fa1d7b5f173932e40cf4578b0ffcd99d0fe0083abd10d426802110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72d832777e2b2701da5dc29e6c9d9e892e79e5f3d092017af67fa753aad9b73a 0.600000000000 1380152 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": 922466, "vin": [ { "gen": { "height": 922456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72d832777e2b2701da5dc29e6c9d9e892e79e5f3d092017af67fa753aad9b73a" } } ], "extra": [ 1, 13, 198, 141, 127, 188, 23, 202, 111, 161, 215, 181, 241, 115, 147, 46, 64, 207, 69, 120, 176, 255, 205, 153, 208, 254, 0, 131, 171, 209, 13, 66, 104, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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