Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 436abf496a69e1e2eb8cd42b9fb36081f03d460737450ee97af0b152d8c201ce

Tx prefix hash: d17c7b280e10f2fd1684ba24a9183e23955f2fffd025b383a5f55aa3a3ee431d
Tx public key: d404d0a95a1f36c371977bcfc55f8f37cb34cd014291c9889c2e53c1609fd715
Timestamp: 1744871348 Timestamp [UCT]: 2025-04-17 06:29:08 Age [y:d:h:m:s]: 00:051:01:27:28
Block: 1263241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36536 RingCT/type: yes/0
Extra: 01d404d0a95a1f36c371977bcfc55f8f37cb34cd014291c9889c2e53c1609fd7150211000000096c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6081a6b204738d5178c00a6da2fe93448b3438d63c9c586aef86e8deb6b29c17 0.600000000000 1750426 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": 1263251, "vin": [ { "gen": { "height": 1263241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6081a6b204738d5178c00a6da2fe93448b3438d63c9c586aef86e8deb6b29c17" } } ], "extra": [ 1, 212, 4, 208, 169, 90, 31, 54, 195, 113, 151, 123, 207, 197, 95, 143, 55, 203, 52, 205, 1, 66, 145, 201, 136, 156, 46, 83, 193, 96, 159, 215, 21, 2, 17, 0, 0, 0, 9, 108, 152, 170, 61, 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