Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5502c045ce76c5dc8f45621cc8f4bdef3e6bb061b05c62de4f7b5659eecac1dc

Tx prefix hash: f781b6784500a978e5cda7853cc44b34da30493891875694f7b44243863a33e6
Tx public key: 4d46c48ba0e02bb1b7f11eef8c9ba99c2dd5a6801fe796c93550923fda05124c
Timestamp: 1711100697 Timestamp [UCT]: 2024-03-22 09:44:57 Age [y:d:h:m:s]: 01:224:16:27:30
Block: 983796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419254 RingCT/type: yes/0
Extra: 014d46c48ba0e02bb1b7f11eef8c9ba99c2dd5a6801fe796c93550923fda05124c0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a55ddb83583bc1e44b8800b55523efbda5c1d160e545749f9e5188f50b2214b 0.600000000000 1443943 of 15

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": 983806, "vin": [ { "gen": { "height": 983796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a55ddb83583bc1e44b8800b55523efbda5c1d160e545749f9e5188f50b2214b" } } ], "extra": [ 1, 77, 70, 196, 139, 160, 224, 43, 177, 183, 241, 30, 239, 140, 155, 169, 156, 45, 213, 166, 128, 31, 231, 150, 201, 53, 80, 146, 63, 218, 5, 18, 76, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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