Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1a54b4dd250489456b70966e88dede44e75a9b03c11162baa8b3527923cadc8

Tx prefix hash: 5ee722e38ef07901a6a7c06f29aa5eac372ff47d5e76a4d2d0f0cb5de2724ccc
Tx public key: 94f9026cc5182c64ccc9445ad01f55bec0b40d4586aa6ce7fdc0c77e9e9031d2
Timestamp: 1735782766 Timestamp [UCT]: 2025-01-02 01:52:46 Age [y:d:h:m:s]: 00:106:12:31:04
Block: 1188269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75932 RingCT/type: yes/0
Extra: 0194f9026cc5182c64ccc9445ad01f55bec0b40d4586aa6ce7fdc0c77e9e9031d2021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86a14cab71f521b7e314d96e60e9228c1848f384af563b431e300be7f4b470ed 0.600000000000 1674770 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": 1188279, "vin": [ { "gen": { "height": 1188269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86a14cab71f521b7e314d96e60e9228c1848f384af563b431e300be7f4b470ed" } } ], "extra": [ 1, 148, 249, 2, 108, 197, 24, 44, 100, 204, 201, 68, 90, 208, 31, 85, 190, 192, 180, 13, 69, 134, 170, 108, 231, 253, 192, 199, 126, 158, 144, 49, 210, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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