Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f888e414d41f7e4ab83ac75c57135cea6f410327f97a3cff163060617dee6da0

Tx prefix hash: c18208091114fe3fcd215af62b532daf034b7e9d45ad7073b4c3ac68f85dac5f
Tx public key: 1cc477f839db226928ab91f0683ca4c0933f55cec6b77a7b4b6046edab4fa46e
Timestamp: 1718967438 Timestamp [UCT]: 2024-06-21 10:57:18 Age [y:d:h:m:s]: 00:267:03:58:05
Block: 1048972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190944 RingCT/type: yes/0
Extra: 011cc477f839db226928ab91f0683ca4c0933f55cec6b77a7b4b6046edab4fa46e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1ed92510b8e1c97b3b13aa255f591cf7b921473247198e9b7c2f621a9db17db 0.600000000000 1519069 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": 1048982, "vin": [ { "gen": { "height": 1048972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1ed92510b8e1c97b3b13aa255f591cf7b921473247198e9b7c2f621a9db17db" } } ], "extra": [ 1, 28, 196, 119, 248, 57, 219, 34, 105, 40, 171, 145, 240, 104, 60, 164, 192, 147, 63, 85, 206, 198, 183, 122, 123, 75, 96, 70, 237, 171, 79, 164, 110, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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