Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6453e54111b7f0361512c5d28797dffea9a28e196379f3132e501ba2cf19e69

Tx prefix hash: b8dde05cbd1ac892da424f173463b8be243f97f183380ad29e4ea08089b9e5a4
Tx public key: f046b6f8c61855e18133517b33ada9dc3f90405b122ae74ae5eea950d70b5eb6
Timestamp: 1577202668 Timestamp [UCT]: 2019-12-24 15:51:08 Age [y:d:h:m:s]: 05:012:08:55:36
Block: 30851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158825 RingCT/type: yes/0
Extra: 01f046b6f8c61855e18133517b33ada9dc3f90405b122ae74ae5eea950d70b5eb60211000000b24fb58672000000000000000000

1 output(s) for total of 485.060288685000 dcy

stealth address amount amount idx
00: 3f09269a6369ac259a6a9c72bcbe9ae2690f79e4bddb88a8a27240b70605377d 485.060288685000 50915 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": 30861, "vin": [ { "gen": { "height": 30851 } } ], "vout": [ { "amount": 485060288685, "target": { "key": "3f09269a6369ac259a6a9c72bcbe9ae2690f79e4bddb88a8a27240b70605377d" } } ], "extra": [ 1, 240, 70, 182, 248, 198, 24, 85, 225, 129, 51, 81, 123, 51, 173, 169, 220, 63, 144, 64, 91, 18, 42, 231, 74, 229, 238, 169, 80, 215, 11, 94, 182, 2, 17, 0, 0, 0, 178, 79, 181, 134, 114, 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