Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52b9b75ce7fd8cbf03a3fc0504c30f1f7d95d8221bb63ee79ea65064fa359a14

Tx prefix hash: 561551908525662aa8a95328cfeaa7e348ea5d0cbbc2f16d276bbca5468d99bc
Tx public key: 359c39acc5b176f8cc84f072f97f602ae9856b46f832f1c78ff76bfb84201059
Timestamp: 1578034651 Timestamp [UCT]: 2020-01-03 06:57:31 Age [y:d:h:m:s]: 04:327:23:59:57
Block: 37582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123649 RingCT/type: yes/0
Extra: 01359c39acc5b176f8cc84f072f97f602ae9856b46f832f1c78ff76bfb842010590211000000078a2ee0d9000000000000000000

1 output(s) for total of 460.761394650000 dcy

stealth address amount amount idx
00: 51ee1dd69b19389558d9201040dbccd5df718c92317153c054d65a0faba56835 460.761394650000 63872 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": 37592, "vin": [ { "gen": { "height": 37582 } } ], "vout": [ { "amount": 460761394650, "target": { "key": "51ee1dd69b19389558d9201040dbccd5df718c92317153c054d65a0faba56835" } } ], "extra": [ 1, 53, 156, 57, 172, 197, 177, 118, 248, 204, 132, 240, 114, 249, 127, 96, 42, 233, 133, 107, 70, 248, 50, 241, 199, 143, 247, 107, 251, 132, 32, 16, 89, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 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