Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc40a55c322092094ebf1024c986c118e3b373e46c8748330dd30bd58bab9303

Tx prefix hash: b046d107fc77b68d6fc92b01c1045dc951caa6e7ee373acd70e36fdcd486f0c6
Tx public key: 752ec5ed449f2bf585a5eb5b3f4c01cb4df6e53c0d756a6d305d169e30bde63e
Timestamp: 1695923139 Timestamp [UCT]: 2023-09-28 17:45:39 Age [y:d:h:m:s]: 01:237:15:13:09
Block: 858147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430936 RingCT/type: yes/0
Extra: 01752ec5ed449f2bf585a5eb5b3f4c01cb4df6e53c0d756a6d305d169e30bde63e02110000000be6d27f9c000000000000000000

1 output(s) for total of 0.880243446000 dcy

stealth address amount amount idx
00: d1ad299f8828c917aa0388a77cfa6b95fc74e7a908df4912b6831a16b94cf192 0.880243446000 1312311 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": 858157, "vin": [ { "gen": { "height": 858147 } } ], "vout": [ { "amount": 880243446, "target": { "key": "d1ad299f8828c917aa0388a77cfa6b95fc74e7a908df4912b6831a16b94cf192" } } ], "extra": [ 1, 117, 46, 197, 237, 68, 159, 43, 245, 133, 165, 235, 91, 63, 76, 1, 203, 77, 246, 229, 60, 13, 117, 106, 109, 48, 93, 22, 158, 48, 189, 230, 62, 2, 17, 0, 0, 0, 11, 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