Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1178e09f6e4eeb5340d73c6ec56036dc3a31304f5ff96c99a0d2aa6b592508a7

Tx prefix hash: 9d1f62890ee6c17728032889b13597cb7cff810f0892857b94e0f23473b8d8b9
Tx public key: f8858ccbaf9c27c90c60b80bfa5c31b562c67e567813250800f934fc7db9748e
Timestamp: 1741835168 Timestamp [UCT]: 2025-03-13 03:06:08 Age [y:d:h:m:s]: 00:296:11:37:03
Block: 1238124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209692 RingCT/type: yes/0
Extra: 01f8858ccbaf9c27c90c60b80bfa5c31b562c67e567813250800f934fc7db9748e0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3860f951270dcc0008b14ac893f8ead3080863028dfc383e3aabfeb08f758ac4 0.600000000000 1725083 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": 1238134, "vin": [ { "gen": { "height": 1238124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3860f951270dcc0008b14ac893f8ead3080863028dfc383e3aabfeb08f758ac4" } } ], "extra": [ 1, 248, 133, 140, 203, 175, 156, 39, 201, 12, 96, 184, 11, 250, 92, 49, 181, 98, 198, 126, 86, 120, 19, 37, 8, 0, 249, 52, 252, 125, 185, 116, 142, 2, 17, 0, 0, 0, 6, 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