Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 355dcc06726c5cacf9a58c37531f754d6f692906d3d01a60dbbffc974c49ed22

Tx prefix hash: 7bbce8f723bc9e71e7bc1284bfd5189064052a2ff4bf476fda4378e38eaff51e
Tx public key: 56a795044a3e1454abc6ef40ae49c0202a17e643a09740b3e5f4c4246c118237
Timestamp: 1695025465 Timestamp [UCT]: 2023-09-18 08:24:25 Age [y:d:h:m:s]: 02:076:14:41:06
Block: 850693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 574463 RingCT/type: yes/0
Extra: 0156a795044a3e1454abc6ef40ae49c0202a17e643a09740b3e5f4c4246c118237021100000003faf35c9c000000000000000000

1 output(s) for total of 0.931753445000 dcy

stealth address amount amount idx
00: 40b08d6845c6b43fa41060da801d945d5932ef6f2bb2e2fe50ad0414143b35c8 0.931753445000 1304427 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": 850703, "vin": [ { "gen": { "height": 850693 } } ], "vout": [ { "amount": 931753445, "target": { "key": "40b08d6845c6b43fa41060da801d945d5932ef6f2bb2e2fe50ad0414143b35c8" } } ], "extra": [ 1, 86, 167, 149, 4, 74, 62, 20, 84, 171, 198, 239, 64, 174, 73, 192, 32, 42, 23, 230, 67, 160, 151, 64, 179, 229, 244, 196, 36, 108, 17, 130, 55, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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