Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f12c4c100c76bbb86ebd15543a35f393ab8c5d1a82a707345146913731276208

Tx prefix hash: 78396aaa5326adc3383810f698f658712cac73052dac4f68158a0a15450f429a
Tx public key: f2c748cc2c85f7665b76739d76f7224d53b237cb8d75333165c771b08f5eb0ae
Timestamp: 1670422013 Timestamp [UCT]: 2022-12-07 14:06:53 Age [y:d:h:m:s]: 02:351:03:37:25
Block: 647416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 770400 RingCT/type: yes/0
Extra: 01f2c748cc2c85f7665b76739d76f7224d53b237cb8d75333165c771b08f5eb0ae0211000000047e406890000000000000000000

1 output(s) for total of 4.393817630000 dcy

stealth address amount amount idx
00: af1d2639e2fd2aa0994fbddea74a2cf82130e7f088683b4d6c9879826d6e78f5 4.393817630000 1087689 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": 647426, "vin": [ { "gen": { "height": 647416 } } ], "vout": [ { "amount": 4393817630, "target": { "key": "af1d2639e2fd2aa0994fbddea74a2cf82130e7f088683b4d6c9879826d6e78f5" } } ], "extra": [ 1, 242, 199, 72, 204, 44, 133, 247, 102, 91, 118, 115, 157, 118, 247, 34, 77, 83, 178, 55, 203, 141, 117, 51, 49, 101, 199, 113, 176, 143, 94, 176, 174, 2, 17, 0, 0, 0, 4, 126, 64, 104, 144, 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