Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4efbf207373cc7ddce0938c78a77549477a98e182d66406995de0aa23b20c9dc

Tx prefix hash: a71fbdde35b0a7481295fca795c33697c776b917a3edb07fbe716f3f379d538b
Tx public key: b3d5ae3f085c382d040ddc39914eca4f4c37432e8f5fe82dc8d0a07351520b13
Timestamp: 1679869871 Timestamp [UCT]: 2023-03-26 22:31:11 Age [y:d:h:m:s]: 01:292:05:39:17
Block: 725767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469723 RingCT/type: yes/0
Extra: 01b3d5ae3f085c382d040ddc39914eca4f4c37432e8f5fe82dc8d0a07351520b1302110000000152542ceb000000000000000000

1 output(s) for total of 2.542686456000 dcy

stealth address amount amount idx
00: f01c03c60bd292183c0c1126c5d95cb6813d9fdb4fece66b6a8f78e1aa8de2b9 2.542686456000 1170958 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": 725777, "vin": [ { "gen": { "height": 725767 } } ], "vout": [ { "amount": 2542686456, "target": { "key": "f01c03c60bd292183c0c1126c5d95cb6813d9fdb4fece66b6a8f78e1aa8de2b9" } } ], "extra": [ 1, 179, 213, 174, 63, 8, 92, 56, 45, 4, 13, 220, 57, 145, 78, 202, 79, 76, 55, 67, 46, 143, 95, 232, 45, 200, 208, 160, 115, 81, 82, 11, 19, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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