Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88528a9326e4b8b7e805fbb75c9b4f081c445b17b84dfbb9f45769c7f77fd154

Tx prefix hash: 7184b1d8cecc8c9f1edfd19eac22d6f7241bbbedc4ceb9b3b5b8179ece8ede0d
Tx public key: cc917a9428e02f6a5c52ec1c4a9ab2c072307362fd59593f8fbd7a7553613385
Timestamp: 1722716608 Timestamp [UCT]: 2024-08-03 20:23:28 Age [y:d:h:m:s]: 00:081:17:02:22
Block: 1080071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58502 RingCT/type: yes/0
Extra: 01cc917a9428e02f6a5c52ec1c4a9ab2c072307362fd59593f8fbd7a7553613385021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5dd28c266cfc55a67528fa346c596a5fa3b4e960a16037a90fcf4f0b189d9e2 0.600000000000 1553292 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": 1080081, "vin": [ { "gen": { "height": 1080071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5dd28c266cfc55a67528fa346c596a5fa3b4e960a16037a90fcf4f0b189d9e2" } } ], "extra": [ 1, 204, 145, 122, 148, 40, 224, 47, 106, 92, 82, 236, 28, 74, 154, 178, 192, 114, 48, 115, 98, 253, 89, 89, 63, 143, 189, 122, 117, 83, 97, 51, 133, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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