Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6543e7d195eb4bc6595119757bfdf8d4322ac2fce0b466702d37af6ab3163fdf

Tx prefix hash: e717e7d0c6fc7aac92012ec58cc4cd0fd23716c6d9d175645637f7e9d8a0f200
Tx public key: 58e0fa8d6ba4d5b50d0d18a9d84d06b07cd1860c7ad8d00928ccb8e05d9adc96
Timestamp: 1661199653 Timestamp [UCT]: 2022-08-22 20:20:53 Age [y:d:h:m:s]: 03:074:03:43:12
Block: 571605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 832799 RingCT/type: yes/0
Extra: 0158e0fa8d6ba4d5b50d0d18a9d84d06b07cd1860c7ad8d00928ccb8e05d9adc96021100000001e6d27f9c000000000000000000

1 output(s) for total of 7.834935961000 dcy

stealth address amount amount idx
00: dcb9f49483241d6c25d2cb1eed888839152f3faebb4e5b30020cde3938f69fec 7.834935961000 1004823 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": 571615, "vin": [ { "gen": { "height": 571605 } } ], "vout": [ { "amount": 7834935961, "target": { "key": "dcb9f49483241d6c25d2cb1eed888839152f3faebb4e5b30020cde3938f69fec" } } ], "extra": [ 1, 88, 224, 250, 141, 107, 164, 213, 181, 13, 13, 24, 169, 216, 77, 6, 176, 124, 209, 134, 12, 122, 216, 208, 9, 40, 204, 184, 224, 93, 154, 220, 150, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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