Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 231688f7967b85f1de53cefc55868faf473a6e0644bdf2d7bb635cbb34d87236

Tx prefix hash: cbfcacb5c613ece9a586cd998d401f959c26beefcc4bef264a21ba9d42df34a3
Tx public key: 5f258174bc08edea1e30a208d7d49030b80a372af282e8e6e84c5591e50569fb
Timestamp: 1713805449 Timestamp [UCT]: 2024-04-22 17:04:09 Age [y:d:h:m:s]: 00:360:12:50:51
Block: 1006198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257746 RingCT/type: yes/0
Extra: 015f258174bc08edea1e30a208d7d49030b80a372af282e8e6e84c5591e50569fb02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1cf982525e5f9259b7e21ed2c81a45f7cc9042116003f2e4e7c3fe88fa84e2f 0.600000000000 1467144 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": 1006208, "vin": [ { "gen": { "height": 1006198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1cf982525e5f9259b7e21ed2c81a45f7cc9042116003f2e4e7c3fe88fa84e2f" } } ], "extra": [ 1, 95, 37, 129, 116, 188, 8, 237, 234, 30, 48, 162, 8, 215, 212, 144, 48, 184, 10, 55, 42, 242, 130, 232, 230, 232, 76, 85, 145, 229, 5, 105, 251, 2, 17, 0, 0, 0, 11, 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