Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5857122a41fdc7c01f865debec52f1787692105774d486c5173b2118c629f8f

Tx prefix hash: e11eb14b971e63f3c91efa2ea81ca627eaab5514c99a0f10fcdd1a18a5b0d29b
Tx public key: 52d461e42ae05c1252e4e06669c56cb07b45afc9c30980890cafc5fc6fe434bf
Timestamp: 1697391892 Timestamp [UCT]: 2023-10-15 17:44:52 Age [y:d:h:m:s]: 01:139:16:34:55
Block: 870332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360838 RingCT/type: yes/0
Extra: 0152d461e42ae05c1252e4e06669c56cb07b45afc9c30980890cafc5fc6fe434bf021100000009faf35c9c000000000000000000

1 output(s) for total of 0.802100559000 dcy

stealth address amount amount idx
00: 15942e882c1e00585038d08e4ed5ae6cf41a5edb9c64506d3a2ae74920b88bcd 0.802100559000 1325211 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": 870342, "vin": [ { "gen": { "height": 870332 } } ], "vout": [ { "amount": 802100559, "target": { "key": "15942e882c1e00585038d08e4ed5ae6cf41a5edb9c64506d3a2ae74920b88bcd" } } ], "extra": [ 1, 82, 212, 97, 228, 42, 224, 92, 18, 82, 228, 224, 102, 105, 197, 108, 176, 123, 69, 175, 201, 195, 9, 128, 137, 12, 175, 197, 252, 111, 228, 52, 191, 2, 17, 0, 0, 0, 9, 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