Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e1b14b154b85b1611944aff5380b7f34e2e3905fa5dbf18a26beb154d14a394

Tx prefix hash: 5205d04e9b23300ff6f869007f372da40f9e55d47f9684c86511490d135dc533
Tx public key: 609b9413a93353e9b57aa504eb9fcbf72aaa493f5dbb3c1b8c3529fd5decd3f2
Timestamp: 1576643635 Timestamp [UCT]: 2019-12-18 04:33:55 Age [y:d:h:m:s]: 04:324:22:13:51
Block: 28322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119189 RingCT/type: yes/0
Extra: 01609b9413a93353e9b57aa504eb9fcbf72aaa493f5dbb3c1b8c3529fd5decd3f202110000000fad433a0b000000000000000000

1 output(s) for total of 494.490920421000 dcy

stealth address amount amount idx
00: c0c74522357d89fb01657274f91c08702e42ab95ec2703cc65d571a1c647c1a4 494.490920421000 46866 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": 28332, "vin": [ { "gen": { "height": 28322 } } ], "vout": [ { "amount": 494490920421, "target": { "key": "c0c74522357d89fb01657274f91c08702e42ab95ec2703cc65d571a1c647c1a4" } } ], "extra": [ 1, 96, 155, 148, 19, 169, 51, 83, 233, 181, 122, 165, 4, 235, 159, 203, 247, 42, 170, 73, 63, 93, 187, 60, 27, 140, 53, 41, 253, 93, 236, 211, 242, 2, 17, 0, 0, 0, 15, 173, 67, 58, 11, 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