Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3326f23099d8d5bee347139252203a1ab1161ee13cfdf46000edc3379903c667

Tx prefix hash: 0ce091ac94dbb8a037e2d086acdd2f659925bedb0647bd516628a89f0a899c47
Tx public key: f00889c4105cc2e80ae6cf90a6fff72570f1d37b3d6fc04fdc0974da79e563e3
Timestamp: 1730660461 Timestamp [UCT]: 2024-11-03 19:01:01 Age [y:d:h:m:s]: 01:015:13:45:54
Block: 1145850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269555 RingCT/type: yes/0
Extra: 01f00889c4105cc2e80ae6cf90a6fff72570f1d37b3d6fc04fdc0974da79e563e30211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 536c0c4deeafa30c3e8ed793f8074e168a415174a0a3e26c70bf0f02c66daee3 0.600000000000 1630375 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": 1145860, "vin": [ { "gen": { "height": 1145850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "536c0c4deeafa30c3e8ed793f8074e168a415174a0a3e26c70bf0f02c66daee3" } } ], "extra": [ 1, 240, 8, 137, 196, 16, 92, 194, 232, 10, 230, 207, 144, 166, 255, 247, 37, 112, 241, 211, 123, 61, 111, 192, 79, 220, 9, 116, 218, 121, 229, 99, 227, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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