Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 657e0c1d31258e15bb914f0cffbc497d3168e3b59f1ec3e2901060e62d20c491

Tx prefix hash: 243055766ae1bf41cb8b5ad8817c10dedc5fbe5892e0b37e52b221d16eabff6e
Tx public key: 61f45f08ad8a632031f0e9457381e40d8040df51bb058230a5b60a3608d53469
Timestamp: 1706362118 Timestamp [UCT]: 2024-01-27 13:28:38 Age [y:d:h:m:s]: 01:134:11:06:12
Block: 944468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357232 RingCT/type: yes/0
Extra: 0161f45f08ad8a632031f0e9457381e40d8040df51bb058230a5b60a3608d5346902110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c91cdc0e18c0da86a701a639c3db89e3a4e7bc1af079f465e776f29020e94c6 0.600000000000 1402718 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": 944478, "vin": [ { "gen": { "height": 944468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c91cdc0e18c0da86a701a639c3db89e3a4e7bc1af079f465e776f29020e94c6" } } ], "extra": [ 1, 97, 244, 95, 8, 173, 138, 99, 32, 49, 240, 233, 69, 115, 129, 228, 13, 128, 64, 223, 81, 187, 5, 130, 48, 165, 182, 10, 54, 8, 213, 52, 105, 2, 17, 0, 0, 0, 7, 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