Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9782e377e60e2c0a491ebaa8f8ff0be75bf02e3ce60a06c300aef4f33878efe1

Tx prefix hash: a013fab6ca316ab0a76e9f8159ef411052d7563b8e600a700ef59414d802ebe9
Tx public key: 791cb15e5d8ec6f1863b29ababae11a1c5fcbe95b7d5526004c5ea5809d497e2
Timestamp: 1703180805 Timestamp [UCT]: 2023-12-21 17:46:45 Age [y:d:h:m:s]: 01:324:10:53:11
Block: 918109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490739 RingCT/type: yes/0
Extra: 01791cb15e5d8ec6f1863b29ababae11a1c5fcbe95b7d5526004c5ea5809d497e20211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45186233fb1bbd786bf0c21f3ae5df2e836d34ec4e914cd5971bc3d4790e840b 0.600000000000 1375747 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": 918119, "vin": [ { "gen": { "height": 918109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45186233fb1bbd786bf0c21f3ae5df2e836d34ec4e914cd5971bc3d4790e840b" } } ], "extra": [ 1, 121, 28, 177, 94, 93, 142, 198, 241, 134, 59, 41, 171, 171, 174, 17, 161, 197, 252, 190, 149, 183, 213, 82, 96, 4, 197, 234, 88, 9, 212, 151, 226, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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