Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc248112f4f5922b4e768459d0034837ed2cf4d82847c70044970ae0c5956eef

Tx prefix hash: 7c0dd9c84c76d114a09d0f2590b1a3650bb0cdd254eebe043a345568d2a21902
Tx public key: f4f3e786d45e26a3c8850f11ab38cb176fb116308029b0bec85b7cbac13fcd4e
Timestamp: 1737551658 Timestamp [UCT]: 2025-01-22 13:14:18 Age [y:d:h:m:s]: 00:147:14:59:17
Block: 1202879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105220 RingCT/type: yes/0
Extra: 01f4f3e786d45e26a3c8850f11ab38cb176fb116308029b0bec85b7cbac13fcd4e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 432bdabe9c9ae39b46d4b705e568c56b58d7b3e7f7108b7471fe1748d43a54b4 0.600000000000 1689546 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": 1202889, "vin": [ { "gen": { "height": 1202879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "432bdabe9c9ae39b46d4b705e568c56b58d7b3e7f7108b7471fe1748d43a54b4" } } ], "extra": [ 1, 244, 243, 231, 134, 212, 94, 38, 163, 200, 133, 15, 17, 171, 56, 203, 23, 111, 177, 22, 48, 128, 41, 176, 190, 200, 91, 124, 186, 193, 63, 205, 78, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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