Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db9ecdc46821923e0f66697b270f016c312f9856bba6f6b7313c5ecffd9b03ae

Tx prefix hash: 1b12a953a9584748a86c74807eceb9404d85842b2bf46733dfb1708ad8ab0e35
Tx public key: 863118188a96d856a411316c3c6f31e3c8a99dbcf8c6a2520ac2aa88c1d41d3e
Timestamp: 1676566630 Timestamp [UCT]: 2023-02-16 16:57:10 Age [y:d:h:m:s]: 02:061:14:40:55
Block: 698356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 565640 RingCT/type: yes/0
Extra: 01863118188a96d856a411316c3c6f31e3c8a99dbcf8c6a2520ac2aa88c1d41d3e021100000004faf35c9c000000000000000000

1 output(s) for total of 2.978904540000 dcy

stealth address amount amount idx
00: 782d30ebd59df376ef7d35db506ef3c5c8141df3819c71e58b49c09e59a45d76 2.978904540000 1141651 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": 698366, "vin": [ { "gen": { "height": 698356 } } ], "vout": [ { "amount": 2978904540, "target": { "key": "782d30ebd59df376ef7d35db506ef3c5c8141df3819c71e58b49c09e59a45d76" } } ], "extra": [ 1, 134, 49, 24, 24, 138, 150, 216, 86, 164, 17, 49, 108, 60, 111, 49, 227, 200, 169, 157, 188, 248, 198, 162, 82, 10, 194, 170, 136, 193, 212, 29, 62, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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