Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fffad58047411a210cbfdfc4a44a9897abf1b6418c87ebd0ebf4b697e9dc71c1

Tx prefix hash: 0534b398999beaf03c176afe956a0885ba011d6eb0ab98ad1435b8571d00ce97
Tx public key: b1ff75219fc4955240a65831892614b942e8b5e2ca7bc22af5ee41c1250d9572
Timestamp: 1698591222 Timestamp [UCT]: 2023-10-29 14:53:42 Age [y:d:h:m:s]: 01:192:10:10:03
Block: 880280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398529 RingCT/type: yes/0
Extra: 01b1ff75219fc4955240a65831892614b942e8b5e2ca7bc22af5ee41c1250d9572021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.743475995000 dcy

stealth address amount amount idx
00: 4f9d35e9e04dde648924c283e8c3a728f85585b1f8be78c8ec1743e755c8f2ba 0.743475995000 1335826 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": 880290, "vin": [ { "gen": { "height": 880280 } } ], "vout": [ { "amount": 743475995, "target": { "key": "4f9d35e9e04dde648924c283e8c3a728f85585b1f8be78c8ec1743e755c8f2ba" } } ], "extra": [ 1, 177, 255, 117, 33, 159, 196, 149, 82, 64, 166, 88, 49, 137, 38, 20, 185, 66, 232, 181, 226, 202, 123, 194, 42, 245, 238, 65, 193, 37, 13, 149, 114, 2, 17, 0, 0, 0, 5, 230, 210, 127, 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