Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28070aeba29b3231a1117f48f4239b3b80d493fbb146e49173677232b3a99115

Tx prefix hash: 405a439b3173300903fe57811ed6e969e905c7d50552d7ce606aa983ba344d0b
Tx public key: 238f96d0c62f47efc6fb33544f4f3249e8cc942869cc25d3322270c6d09fefdc
Timestamp: 1712476149 Timestamp [UCT]: 2024-04-07 07:49:09 Age [y:d:h:m:s]: 01:071:00:10:56
Block: 995154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311660 RingCT/type: yes/0
Extra: 01238f96d0c62f47efc6fb33544f4f3249e8cc942869cc25d3322270c6d09fefdc02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63cd3a0ba8eeb31b59d0867298a0f7ed167ebfe0a1d03a42ae1a0d84de5b581e 0.600000000000 1455560 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": 995164, "vin": [ { "gen": { "height": 995154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63cd3a0ba8eeb31b59d0867298a0f7ed167ebfe0a1d03a42ae1a0d84de5b581e" } } ], "extra": [ 1, 35, 143, 150, 208, 198, 47, 71, 239, 198, 251, 51, 84, 79, 79, 50, 73, 232, 204, 148, 40, 105, 204, 37, 211, 50, 34, 112, 198, 208, 159, 239, 220, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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