Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f4d8d5e5187edd3e332ad574b1cdeab20f3a3894bf67aeca927603342c6b39c

Tx prefix hash: 5c4735be8379b0fbb0b9d191f7b0c3b5fddf6fa5aba91cc0429cfbeccb5b18f2
Tx public key: 3708ddd4ff89863c59fda071f96bc30165b1c541f5ef4029e9fa526bb6e64d4f
Timestamp: 1674372425 Timestamp [UCT]: 2023-01-22 07:27:05 Age [y:d:h:m:s]: 02:102:02:10:10
Block: 680153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594633 RingCT/type: yes/0
Extra: 013708ddd4ff89863c59fda071f96bc30165b1c541f5ef4029e9fa526bb6e64d4f0211000000035029cbac000000000000000000

1 output(s) for total of 3.422714766000 dcy

stealth address amount amount idx
00: 280f768fa294975d1a70b074746db4608aa09878c7b2a80876d7c705e18a684e 3.422714766000 1122180 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": 680163, "vin": [ { "gen": { "height": 680153 } } ], "vout": [ { "amount": 3422714766, "target": { "key": "280f768fa294975d1a70b074746db4608aa09878c7b2a80876d7c705e18a684e" } } ], "extra": [ 1, 55, 8, 221, 212, 255, 137, 134, 60, 89, 253, 160, 113, 249, 107, 195, 1, 101, 177, 197, 65, 245, 239, 64, 41, 233, 250, 82, 107, 182, 230, 77, 79, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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