Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bdc3c25262ec607d3b0740becfd0300fec1a86a91012947b8fad7fa84997995

Tx prefix hash: 427357b49c31ef65746de9cfdc6dabaf75bcd09b0c48b2982405e06eab994c8f
Tx public key: 0e232f3053c8904d93b32474ce47d51273d9158391ec409e1edc11ccf1e517f2
Timestamp: 1577935277 Timestamp [UCT]: 2020-01-02 03:21:17 Age [y:d:h:m:s]: 05:001:00:58:17
Block: 36881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150743 RingCT/type: yes/0
Extra: 010e232f3053c8904d93b32474ce47d51273d9158391ec409e1edc11ccf1e517f20211000000174943cd9f000000000000000000

1 output(s) for total of 463.232252169000 dcy

stealth address amount amount idx
00: 40772b958e3a550c8fe5299ba60484489c0a43bdb6ba9a246c50afeab6c70eb8 463.232252169000 62523 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": 36891, "vin": [ { "gen": { "height": 36881 } } ], "vout": [ { "amount": 463232252169, "target": { "key": "40772b958e3a550c8fe5299ba60484489c0a43bdb6ba9a246c50afeab6c70eb8" } } ], "extra": [ 1, 14, 35, 47, 48, 83, 200, 144, 77, 147, 179, 36, 116, 206, 71, 213, 18, 115, 217, 21, 131, 145, 236, 64, 158, 30, 220, 17, 204, 241, 229, 23, 242, 2, 17, 0, 0, 0, 23, 73, 67, 205, 159, 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