Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2d94a8dca2aa3915bc1ec1a653968f2385ac99892f43581ea6d9eb4faaff146

Tx prefix hash: 47a0eed20eeebe6882de7ed649f5f0c74d1bc5cfd01a2c4f5a2c29322f788f53
Tx public key: d37222758ef26cd08a75a69d6342b10ac4ab2cc9cd138f0e68bf837e4d239d0d
Timestamp: 1707688404 Timestamp [UCT]: 2024-02-11 21:53:24 Age [y:d:h:m:s]: 01:054:06:56:07
Block: 955478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299849 RingCT/type: yes/0
Extra: 01d37222758ef26cd08a75a69d6342b10ac4ab2cc9cd138f0e68bf837e4d239d0d02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab225266572e512d3fa670a307dfb67775f1f1f1cb771ff0f84918382c51f1b4 0.600000000000 1414768 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": 955488, "vin": [ { "gen": { "height": 955478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab225266572e512d3fa670a307dfb67775f1f1f1cb771ff0f84918382c51f1b4" } } ], "extra": [ 1, 211, 114, 34, 117, 142, 242, 108, 208, 138, 117, 166, 157, 99, 66, 177, 10, 196, 171, 44, 201, 205, 19, 143, 14, 104, 191, 131, 126, 77, 35, 157, 13, 2, 17, 0, 0, 0, 10, 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