Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9ee5d66cd46ca8c0170e865e0cfd58495d063445ab7d8a10528c4afcff6a328

Tx prefix hash: bc5f71b76790a923dd92a6f7c19c4107b593aa78eab1009be5f067d96bdf0aac
Tx public key: 3ec6a8b3a4e11aa03077e9e803811f18e4650eb7178c8e9cb98c8332c6cd998d
Timestamp: 1673174669 Timestamp [UCT]: 2023-01-08 10:44:29 Age [y:d:h:m:s]: 01:312:17:51:47
Block: 670204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484535 RingCT/type: yes/0
Extra: 013ec6a8b3a4e11aa03077e9e803811f18e4650eb7178c8e9cb98c8332c6cd998d02110000000174b6d784000000000000000000

1 output(s) for total of 3.692630819000 dcy

stealth address amount amount idx
00: 9d7c5511a19cde530558ade536b3f2d446edcf72aa83b816b7fee951859118bc 3.692630819000 1111591 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": 670214, "vin": [ { "gen": { "height": 670204 } } ], "vout": [ { "amount": 3692630819, "target": { "key": "9d7c5511a19cde530558ade536b3f2d446edcf72aa83b816b7fee951859118bc" } } ], "extra": [ 1, 62, 198, 168, 179, 164, 225, 26, 160, 48, 119, 233, 232, 3, 129, 31, 24, 228, 101, 14, 183, 23, 140, 142, 156, 185, 140, 131, 50, 198, 205, 153, 141, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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