Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7206c58180c7e5a027da9fa5b57b5d02208359d24da70c0c5669e149e08a2ab7

Tx prefix hash: 74b8916e34eec20ed8d9b2919741cc3c303a4a1cf28f5f2172b906df9588ae25
Tx public key: 9f54fbb0d93dc69220888c1db0cdf0e6f5ef3b8c0242bfc4fdd49b1092505a39
Timestamp: 1577061356 Timestamp [UCT]: 2019-12-23 00:35:56 Age [y:d:h:m:s]: 05:024:17:35:40
Block: 29785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1167554 RingCT/type: yes/0
Extra: 019f54fbb0d93dc69220888c1db0cdf0e6f5ef3b8c0242bfc4fdd49b1092505a39021100000011ad433a0b000000000000000000

1 output(s) for total of 489.055117771000 dcy

stealth address amount amount idx
00: cdb39d5873588c5084691b9c8f047e71357bbc7072b3b299d4c54a6d33fd54d5 489.055117771000 49085 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": 29795, "vin": [ { "gen": { "height": 29785 } } ], "vout": [ { "amount": 489055117771, "target": { "key": "cdb39d5873588c5084691b9c8f047e71357bbc7072b3b299d4c54a6d33fd54d5" } } ], "extra": [ 1, 159, 84, 251, 176, 217, 61, 198, 146, 32, 136, 140, 29, 176, 205, 240, 230, 245, 239, 59, 140, 2, 66, 191, 196, 253, 212, 155, 16, 146, 80, 90, 57, 2, 17, 0, 0, 0, 17, 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