Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a98cdf578843c2e13995355ae5d43c52aaf1bf1d28fd317b2fec11120fabeb8

Tx prefix hash: 1fb6ec73a8972c24b266e98f5592d953cb5d6c6c2750ab6f5904759e0c479cc7
Tx public key: f3319d81104720c7f21f4838e45235c8fb1bd758eb3ab3f5968618c5623ac0e7
Timestamp: 1708472051 Timestamp [UCT]: 2024-02-20 23:34:11 Age [y:d:h:m:s]: 01:121:16:01:42
Block: 961981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347866 RingCT/type: yes/0
Extra: 01f3319d81104720c7f21f4838e45235c8fb1bd758eb3ab3f5968618c5623ac0e7021100000001d49b3c67000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2867ed8114e20584f02d32b0049dbfc3bb578ae9fe6ff1dedc4f1eb70c02eec6 0.600000000000 1421604 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": 961991, "vin": [ { "gen": { "height": 961981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2867ed8114e20584f02d32b0049dbfc3bb578ae9fe6ff1dedc4f1eb70c02eec6" } } ], "extra": [ 1, 243, 49, 157, 129, 16, 71, 32, 199, 242, 31, 72, 56, 228, 82, 53, 200, 251, 27, 215, 88, 235, 58, 179, 245, 150, 134, 24, 197, 98, 58, 192, 231, 2, 17, 0, 0, 0, 1, 212, 155, 60, 103, 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