Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c8aa0676bf5841ba2ac79c371d67ff2fb677842796409042941fb5ae6d8688f

Tx prefix hash: 14a471bb56a76da7e18565f80fcde892e872d4c3d7242342779b09e648dd114a
Tx public key: f899b56464fdef8ef6a9c948c54c04f8f11d67abf33dad33fb87b53068a380ca
Timestamp: 1698471222 Timestamp [UCT]: 2023-10-28 05:33:42 Age [y:d:h:m:s]: 01:154:02:57:21
Block: 879287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371135 RingCT/type: yes/0
Extra: 01f899b56464fdef8ef6a9c948c54c04f8f11d67abf33dad33fb87b53068a380ca021100000005faf35c9c000000000000000000

1 output(s) for total of 0.749129972000 dcy

stealth address amount amount idx
00: ffb8496aa154f6f3119ba3371dbd6d55067bb6db7ef86b84ec0b23512058a5b5 0.749129972000 1334797 of 0

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": 879297, "vin": [ { "gen": { "height": 879287 } } ], "vout": [ { "amount": 749129972, "target": { "key": "ffb8496aa154f6f3119ba3371dbd6d55067bb6db7ef86b84ec0b23512058a5b5" } } ], "extra": [ 1, 248, 153, 181, 100, 100, 253, 239, 142, 246, 169, 201, 72, 197, 76, 4, 248, 241, 29, 103, 171, 243, 61, 173, 51, 251, 135, 181, 48, 104, 163, 128, 202, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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