Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5498bde888a4ad9ec0ef430efe578510d2b9620cae75806e784f89314a664ffe

Tx prefix hash: 03c023de7f17a7c814e7e60d5a4d416e9f24c5f9b99d8e5614997b67b3073a47
Tx public key: 546e2e4ffa2641500d1b2b887092bc83fd850f4b3c20a80bccdaf5243ecf3463
Timestamp: 1578671441 Timestamp [UCT]: 2020-01-10 15:50:41 Age [y:d:h:m:s]: 05:098:06:42:10
Block: 42814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1220188 RingCT/type: yes/0
Extra: 01546e2e4ffa2641500d1b2b887092bc83fd850f4b3c20a80bccdaf5243ecf3463021100000001d81c26c0000000000000000000

1 output(s) for total of 442.731363176000 dcy

stealth address amount amount idx
00: b2a341c3d099c94831e413a84ce2677d2b8bbcd350c99b20855206f8a9629b75 442.731363176000 77258 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": 42824, "vin": [ { "gen": { "height": 42814 } } ], "vout": [ { "amount": 442731363176, "target": { "key": "b2a341c3d099c94831e413a84ce2677d2b8bbcd350c99b20855206f8a9629b75" } } ], "extra": [ 1, 84, 110, 46, 79, 250, 38, 65, 80, 13, 27, 43, 136, 112, 146, 188, 131, 253, 133, 15, 75, 60, 32, 168, 11, 204, 218, 245, 36, 62, 207, 52, 99, 2, 17, 0, 0, 0, 1, 216, 28, 38, 192, 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