Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 439c3e45b8086b24d2f8d406ec7419827b7d0ef7afef9285eed7306c7bd6c26e

Tx prefix hash: 7c2ceb747dc1f194a955a70ad8d6461094f38def56481a839e892a885d8f604e
Tx public key: a6cff85675d4fc09a3655f4ac7ca36f434638a291435c0d9bb6d1bb7d646db23
Timestamp: 1725808352 Timestamp [UCT]: 2024-09-08 15:12:32 Age [y:d:h:m:s]: 00:189:11:43:51
Block: 1105712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135262 RingCT/type: yes/0
Extra: 01a6cff85675d4fc09a3655f4ac7ca36f434638a291435c0d9bb6d1bb7d646db2302110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd780ce19b9d028b4421d7c8338a55fd311fba07defc2f09ab718bc17245a9cb 0.600000000000 1583143 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": 1105722, "vin": [ { "gen": { "height": 1105712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd780ce19b9d028b4421d7c8338a55fd311fba07defc2f09ab718bc17245a9cb" } } ], "extra": [ 1, 166, 207, 248, 86, 117, 212, 252, 9, 163, 101, 95, 74, 199, 202, 54, 244, 52, 99, 138, 41, 20, 53, 192, 217, 187, 109, 27, 183, 214, 70, 219, 35, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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